Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

• If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

• If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

• Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

• README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

• Entry returns a single plugin spec with the new plugin as the only top level spec (not applicable for recipes or packs).

• Proper usage of opts table rather than setting things up with the config function.

• Proper usage of specs table for all specs that are not dependencies of a given plugin (not applicable for recipes or packs).

Hello @Uzaaft, thanks for the comment.

I was actually using zig implementation as a base

Sorry, I am quite new to nvim/vim env 😅 (Still, I should have checked better the other implementations)

• I have included odinfmt via conform.nvim following the same patterns as the elm/go packs
• odinfmt ships bundled with the ols mason package, so I think there's no extra mason-tool-installer entry needed
• I am not providing any DAP since I didn't found Odin-specific debug adapter in mason

I've saw some other languages like crystal have a generic config

I can try add it, but right now I just wanted to share some basic setup

@kuroski That's gaps in the other packs we hopefully should patch eventually :)